<!DOCTYPE html>
<html xmlns:wicket="http://wicket.apache.org">
<head>
<wicket:head>
	<title>Wicket - jQuery UI</title>
</wicket:head>
</head>
<body>
    <wicket:extend>
        <h2>Welcome!</h2>
        <div>
            Welcome to the demo site of the <b>Wicket - jQuery UI</b> project.<br/>
            <br/>
            The goal of this project is to provide a bridge between Wicket and jQuery UI.<br/>
            The 'core' provides all jQuery UI built-in components.<br/>
            <br/>
            Apache Wicket: <a href="http://wicket.apache.org/">http://wicket.apache.org</a><br/>
            jQuery UI: <a href="http://jqueryui.com/">http://jqueryui.com</a><br/>
            Wicket - jQuery UI: <a href="http://code.google.com/p/wicket-jquery-ui/">http://code.google.com/p/wicket-jquery-ui/</a><br/>
            <br />
            Do not hesitate to leave a comment or ask a question in the <a href="https://groups.google.com/forum/?fromgroups#!forum/wicket-jquery-ui">forum</a>, or to open an issue if you encounter any problem: <a href="http://code.google.com/p/wicket-jquery-ui/issues/list">here</a>.
        </div>
        <br/>
        <h3>About this demo site</h3>
        <div>
        	This demo site aims to present all behaviors &#38; widgets (components) the API provides, including all jQuery UI components you may find on the <a href="http://jqueryui.com/demos/accordion/" target="jquery-ui">Query UI demo site</a>.<br/>
        	<br/>
        	For each main component class in the left's list, you may find several other related components (or other samples), including wicket-jquery-ui original ones (like message dialog-boxes or secured-button).<br />
        </div>
        <br/>
        <h3>Why this project?</h3>
        <div>
            I began with Wicket several years ago. I also wanted to use a javascript UI framework in addition to Wicket to have a "cool" rendering and was quickly drawn to jQuery UI.<br />
            <br/>
            I explored several other existing projects (wiQuery, JQWicket), but I realized they did not met my expectations I had about such an integration. The idea I had, was to have an API where using supplied components should have been in the same way than using Wicket built-in ones.<br/>
            <br/>
            So, I developed a first version of a Wicket - jQuery UI integration at work. The webapp that is using the developed API has been in production for 3 years and satisfies all the original aims.<br/>
            <br/>
            When the Wicket team released the 1.5 version then... a lot of things had changed from 1.4! The technical migration from 1.4 to 1.5 also had consequences for the API that I'd done. And of course, I had no time (and no budget) to perform this migration. That's why I rewrote this integration from scratch, in my spare time, so I will be able to reuse it at work.<br/>
            <br/>
            Thus began this open source project...<br/>
        </div>
        <br/>
        <h3>Getting started</h3>
        <div>
            In order to get started using this API, you may download appropriate jar(s) or set a maven dependency.<br/>
            <h4>Download jar(s)</h4>
            <div>
                If you are not using maven, you need to download the core jar here: <a href="http://code.google.com/p/wicket-jquery-ui/downloads/list">http://code.google.com/p/wicket-jquery-ui/downloads/list</a><br/>
                You may also download other jars as required (ie: jquery-ui-kendo). Once done, just include the jar(s) in your project's build path.
            </div>
            <h4>Using Maven</h4>
            <div>
                <pre>
&lt;dependency&gt;
    &lt;groupId&gt;com.googlecode.wicket-jquery-ui&lt;/groupId&gt;
    &lt;artifactId&gt;jquery-ui-core&lt;/artifactId&gt;
    &lt;version&gt;1.0&lt;/version&gt;
&lt;/dependency&gt;
                </pre>
                You might need to define the repository (either in your pom.xml or settings.xml)
                <pre>
&lt;repositories&gt;
	&lt;repository&gt;
		&lt;id&gt;sonatype-releases&lt;/id&gt;
		&lt;name&gt;Sonatype Releases Repository&lt;/name&gt;
		&lt;url&gt;http://oss.sonatype.org/content/repositories/releases/&lt;/url&gt;
	&lt;/repository&gt;
&lt;/repositories&gt; 
				</pre>
                If the version you specified is 'snapshot', you might define this repository:
                <pre>
&lt;repositories&gt;
	&lt;repository&gt;
		&lt;id&gt;sonatype-snapshots&lt;/id&gt;
		&lt;name&gt;Sonatype Snapshots Repository&lt;/name&gt;
		&lt;url&gt;http://oss.sonatype.org/content/repositories/snapshots/&lt;/url&gt;
		&lt;snapshots&gt;
			&lt;enabled&gt;true&lt;/enabled&gt;
		&lt;/snapshots&gt;
	&lt;/repository&gt;
&lt;/repositories&gt; 
				</pre>
            </div>
            <h4>Setting up the HTML markup</h4>
            <div>
                jQuery UI needs a CSS to work. No jQuery UI CSS has been shipped in the API, so you are free to use the one you wish.<br/>
                You can get your own CSS at <a href="http://jqueryui.com/themeroller/">http://jqueryui.com/themeroller/</a>, and put it (the CSS only) into your website.<br/>
                <br/>
                The base template page is the following: (you might change the CSS href accordingly)
                <pre>
&lt;!DOCTYPE html&gt;
&lt;html xmlns:wicket="http://wicket.apache.org"&gt;
&lt;head&gt;
    &lt;link rel="stylesheet" type="text/css" href="styles/jquery-ui-1.8.19.custom.css" media="all" /&gt;
&lt;/head&gt;
&lt;body&gt;
&lt;/body&gt;
&lt;/html&gt;
                </pre>
            </div>
            <h4>You are now ready to use wicket-jquery-ui!</h4>
            <div>
            Look at the samples provided here to get started with the code...
            </div>
        </div>
    </wicket:extend>
</body>
</html>